From: Behnam Esfahbod Date: Fri, 1 Sep 2017 19:29:22 +0000 (-0700) Subject: [doc] Redirect /policies.html to crates.io/policies X-Git-Tag: archive/raspbian/0.35.0-2+rpi1~3^2^2^2^2^2^2^2~22^2~6^2~65^2~2 X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/success//%22http:/www.example.com/cgi/success/?a=commitdiff_plain;h=9e0cbf106df5a06b8fb35d59967c2734f457f4c4;p=cargo.git [doc] Redirect /policies.html to crates.io/policies This relieves us from migrating the Package Policies document into the new Cargo Manual mdbook. Moved the content to `crates.io` repo in . NOTE: We should wait until that change goes live before landing this one. I'll notify here when it's time to land. Closes --- diff --git a/src/ci/dox.sh b/src/ci/dox.sh index c9417044f..7dffde265 100644 --- a/src/ci/dox.sh +++ b/src/ci/dox.sh @@ -2,12 +2,12 @@ set -ex DOCS="index faq config guide manifest build-script pkgid-spec crates-io \ environment-variables specifying-dependencies source-replacement \ - policies external-tools" + external-tools" ASSETS="CNAME images/noise.png images/forkme.png images/Cargo-Logo-Small.png \ stylesheets/all.css stylesheets/normalize.css javascripts/prism.js \ javascripts/all.js stylesheets/prism.css images/circle-with-i.png \ images/search.png images/org-level-acl.png images/auth-level-acl.png \ - favicon.ico" + favicon.ico policies.html" for asset in $ASSETS; do mkdir -p `dirname target/doc/$asset` diff --git a/src/doc/MIGRATION_MAP b/src/doc/MIGRATION_MAP index ce8d79183..4eb365d45 100644 --- a/src/doc/MIGRATION_MAP +++ b/src/doc/MIGRATION_MAP @@ -7,7 +7,6 @@ environment-variables.md book/src/reference/environment-variables.md external-tools.md book/src/reference/external-tools.md manifest.md book/src/reference/manifest.md pkgid-spec.md book/src/reference/pkgid-spec.md -policies.md book/src/reference/policies.md source-replacement.md book/src/reference/source-replacement.md specifying-dependencies.md book/src/reference/specifying-dependencies.md faq.md book/src/faq.md diff --git a/src/doc/policies.html b/src/doc/policies.html new file mode 100644 index 000000000..2a0146984 --- /dev/null +++ b/src/doc/policies.html @@ -0,0 +1,10 @@ + + + + + + + + Redirecting to https://crates.io/policies... + + diff --git a/src/doc/policies.md b/src/doc/policies.md deleted file mode 100644 index ff3b6a620..000000000 --- a/src/doc/policies.md +++ /dev/null @@ -1,70 +0,0 @@ -% Crates.io package policies - -In general, these policies are guidelines. Problems are often contextual, and -exceptional circumstances sometimes require exceptional measures. We plan to -continue to clarify and expand these rules over time as new circumstances -arise. If your problem is not described below, consider [sending us an email]. - -# Package Ownership - -We have a first-come, first-served policy on crate names. Upon publishing a -package, the publisher will be made owner of the package on Crates.io. - -If someone wants to take over a package, and the previous owner agrees, the -existing maintainer can add them as an owner, and the new maintainer can remove -them. If necessary, the team may reach out to inactive maintainers and help -mediate the process of ownership transfer. - -# Removal - -Many questions are specialized instances of a more general form: âUnder what -circumstances can a package be removed from Crates.io?â - -The short version is that packages are first-come, first-served, and we wonât -attempt to get into policing what exactly makes a legitimate package. We will -do what the law requires us to do, and address flagrant violations of the Rust -Code of Conduct. - -## Squatting - -We do not have any policies to define 'squatting', and so will not hand over -ownership of a package for that reason. - -## The Law - -For issues such as DMCA violations, trademark and copyright infringement, -Crates.io will respect Mozilla Legalâs decisions with regards to content that -is hosted. - -## Code of Conduct - -The Rust project has a [Code of Conduct] which governs appropriate conduct for -the Rust community. In general, any content on Crates.io that violates the Code -of Conduct may be removed. Here, content can refer to but is not limited to: - -- Package Name -- Package Metadata -- Documentation -- Code - -There are two important, related aspects: - -- We will not be pro-actively monitoring the site for these kinds of violations, - but relying on the community to draw them to our attention. -- âDoes this violate the Code of Conductâ is a contextual question that - cannot be directly answered in the hypothetical sense. All of the details - must be taken into consideration in these kinds of situations. - -# Security - -Cargo and crates.io are projects that are governed by the Rust Programming -Language Team. Safety is one of the core principles of Rust, and to that end, -we would like to ensure that cargo and crates.io have secure implementations. -To learn more about disclosing security vulnerabilities, please reference the -[Rust Security policy] for more details. - -Thank you for taking the time to responsibly disclose any issues you find. - -[Rust Security policy]: https://www.rust-lang.org/security.html -[Code of Conduct]: https://www.rust-lang.org/conduct.html -[sending us an email]: mailto:help@crates.io